Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[RFC] Test clang-tidy --checks performance-move-const-arg #29931

Closed

Conversation

fwyzard
Copy link
Contributor

@fwyzard fwyzard commented May 21, 2020

@cmsbuild
Copy link
Contributor

The code-checks are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

-code-checks

ERROR: Build errors found during clang-tidy run.

DataFormats/Common/interface/Wrapper.h:92:80: error: no matching constructor for initialization of 'MkFitInputWrapper' [clang-diagnostic-error]
  Wrapper<T>::Wrapper(Emplace, Args&&... args) : WrapperBase(), present(true), obj(std::forward<Args>(args)...) {}
                                                                               ^
FWCore/Framework/interface/Event.h:448:43: note: in instantiation of function template specialization 'edm::Wrapper<MkFitInputWrapper>::Wrapper<MkFitHitIndexMap, std::vector<std::vector<mkfit::Hit, std::allocator<mkfit::Hit> >, std::allocator<std::vector<mkfit::Hit, std::allocator<mkfit::Hit> > > >, std::vector<mkfit::Track, std::allocator<mkfit::Track> >, mkfit::LayerNumberConverter &>' requested here
--
gmake: *** [config/SCRAM/GMake/Makefile.coderules:128: code-checks] Error 2
gmake: *** [There are compilation/build errors. Please see the detail log above.] Error 2

@slava77
Copy link
Contributor

slava77 commented Jun 10, 2020

+1
(no significant objections/concerns)

it looks like this better not be automated

@santocch
Copy link

+1

@pohsun
Copy link

pohsun commented Jun 20, 2020

+1

@alja
Copy link
Contributor

alja commented Jun 21, 2020

+1

@mrodozov
Copy link
Contributor

mrodozov commented Jul 1, 2020

@fwyzard what we wanted to do with this, could you remind me

@fwyzard
Copy link
Contributor Author

fwyzard commented Jul 1, 2020

This should go in - it's mostly signed, and it actually helped find bugs in our code.

@jfernan2
Copy link
Contributor

jfernan2 commented Jul 1, 2020

+1

@kpedro88
Copy link
Contributor

kpedro88 commented Jul 1, 2020

+upgrade

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment